home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Eagles Nest BBS 8
/
Eagles_Nest_Mac_Collection_Disc_8.TOAST
/
Developer Tools⁄Additions
/
VoodooM10d24
/
VoodooMonkey 1.0d24
/
VoodooMonkey goodies
/
DebuggerINIT User API
/
Read Me
< prev
next >
Wrap
Text File
|
1994-06-06
|
1KB
|
31 lines
DebuggerINIT User API
Mike Lockwood
June 6, 1994
"DebuggerINIT User API" consists of a header file and glue code for communicating
with the VoodooMonkey DebuggerINIT. This is a subset of the full API, containing
only routines that might be useful for VoodooMonkey users.
NubNewObject and NubObjectFreed are used to implement support for the VoodooMonkey
inspector window. Look at MacApp 3.1 for an example of how to do this.
NubRegisterFile, NubTrackResource and NubResourceLoaded are used to support debugging
code that is not loaded by the Resource Manager. For example, if whoever loads your
code calls DetachResource or BlockMove, DebuggerINIT won't know where it is loaded
by default. NubRegisterFile registers your file so it can be debugged. After you
call NubRegisterFile and get a NubFileID, you call NubTrackResource for each resource
in the file that you want to debug. Then whenever one of your resources is loaded
into memory (by whatever means) call NubResourceLoaded to tell DebuggerINIT where
it is loaded.
Warning! This feature has not been tested very much, and is even more unsupported
than the rest of VoodooMonkey/DebuggerINIT. But people asked for it, so I am releasing
this information.
NubAmIBeingDebugged and NubStartDebuggingMe are used to find out if you are being
debugged or requesting to be debugged. This can be useful if you want to only use
SysBreak, SysBreakStr, and SysBreakFunc if there is someone listening.
Have fun!
Mike